docs(audiences): remove Trial plan from Audiences access — Growth or above now required#1561
Merged
george-dilthey merged 1 commit intoJul 14, 2026
Conversation
… now require Growth or above
Contributor
george-dilthey
marked this pull request as ready for review
July 14, 2026 22:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Updated
docs/audiences.mdto remove Trial workspaces from the list of plans with Clay Audiences access. Specifically:Why
A code change in this deploy (
c8bdc8a...b5167da) — commite50042a3— runs a permanent DB migration that setsenableAudiencesGA = falsefor all trial billing plans (trial,trialApril2023,postPricingChange2026Trial). Going forward, new trial workspaces (with a billing plan start date on or after July 16, 2026) will receive no Audiences access. Workspaces created before July 16 on trial plans retain access temporarily via an Eppo flag, but that is a transitional mechanism, not a customer-facing entitlement. The docs claimed Trial workspaces had access to core Audiences features (CSV imports, people/company search, Clay table sends), which is no longer accurate for new trial users.Deploy: clay-run/clay-base
c8bdc8a...b5167da— https://github.com/clay-run/clay-base/actions/runs/29367699690Source link(s)
apps/api/migrations/20260713153000-disable-audiences-ga-for-trial-plans.js— setsenableAudiencesGA = falsefor['trial', 'trialApril2023', 'postPricingChange2026Trial']viaUPDATE clay_admin.billing_plansapps/api/v3/audiences/routes/audience-routes-common-utils.ts:19—EXISTING_TRIAL_AUDIENCES_CUTOFF_MS = Date.UTC(2026, 6, 16)(July 16, 2026);isAudiencesEnabledForWorkspace()returnsfalsefor trial workspaces whose billing plan started on/after that datelibs/shared/src/billing/plan.ts:119—TRIAL_PLAN_DEFAULT_FEATURE_FLAGS.EnableAudiencesGA: falseconfirmedEnableAudiencesGA: trueatplan.ts:165)Uncertainties
None. The verifier returned PASS with file:line evidence for both the DB migration and the runtime gating logic. No Slack discrepancies found. The transitional Eppo grant for existing trials is an implementation detail not requiring customer-facing documentation.
Related observations
docs/audiences.md: docs(audiences): document nested sub-field mapping in bulk enrichments #1558 (sub-field mapping), docs(audiences): add CSV export workaround via Add to workbook #1550 (CSV export via Add to workbook — mentions "trial workspaces" only in Clay table CSV export context, unrelated to plan access), docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547 (deduplication FAQ), docs(audiences): document Salesforce custom object export limitation and workaround #1528 (signal data FAQ), docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507 (Snowflake/BigQuery field mapping), docs(audiences): add Databricks as beta import source #1485 (Databricks import). None cover the plan availability section modified here. Reviewer should reconcile at merge time.Confidence: high
Closes DOC-1157